This page sets governance limits on items that can become excessive. Without limitations, these settings can heavily impact the client and system performance NEGATIVELY.
Element Trees Limits
The element trees exposed in the Discover Pro and Discover Lite tools can retrieve enormous hierarchies that can number into the millions of member elements. While this is highly convenient, the size of the data footprint and the handling the browser can overwhelm many client machines and strain the network. As such, it is good practice to limit these.
The limits can be set independently for desktop machines and tablets (which typically have less computing power).
Slicers Limits
Like element trees, slicer lists exposed in the application can retrieve enormous hierarchies that can number into the millions of member elements. While this is highly convenient, the size of the data footprint and the handling the browser can overwhelm many client machines and strain the network.
- The limit set in the admin is the MASTER limit on slicers for the entire system.
- Slicer limits can then be separately set within User Defaults, which are then assigned to different tenants - but they cannot exceed the master limit set here.
- Next, each user can set their own default slicer limit in their personalized user defaults page (which can not exceed the tenant default).
- Finally, the each slicer used in the system can have a custom limit set through its advanced settings.
Query Limits
The master settings governing the maximum number of rows in the following circumstances:
- Result Limit: The master setting governing the maximum number of rows returned in any single query from the server to the client.
- Export Result Limit: The maximum number of rows that can be printed or exported to a *.csv file.
- ODATA Result Limit: The maximum number of rows inside ODATA reports.
- SQL Result Limit: The maximum number of rows allowed when making use of the inner query mechanism, before Java processing and so on.
The master settings are global, but there is also a per-report Row Limit option in Discover. Pyramid uses whichever is the lower of the two limits.
Tip: You should reset these global query limits based on the performance of your system, focusing particularly on any Out Of Memory errors that you experience.
Export, Printing, and Publication Limits
These settings control the length of time to allow the printing and publishing engines to run before timing out:
- Real time: The limit in seconds for user initiated print or export jobs.
- Batch time: The limit in seconds for publishing jobs launched via schedules.
- Select the Enable retries checkbox to retry the publish action until it either succeeds or reaches the retry limit.